Method and apparatus for persistent connections to a device through the use of multiple physical network connections and connection hand-offs between multiple bands, modes and networks

ABSTRACT

Embodiments communicate messages between mobile devices and destination devices. An exemplary embodiment includes a first border server operable to establish a first communication connection to the mobile device over a first network operating under a first protocol, a second border server operable to establish a second communication connection to the mobile device over a second network operating under a second protocol, and a transport management server communicatively coupled to the first border server and the second border server, and operable to establish a third communication connection to the destination device over a third network operating under a third protocol. The first protocol is configured to communicate a first encapsulated portion of the message. The second protocol is configured to communicate a second encapsulated portion of the message. The third protocol is configured to communicate the first encapsulated portion of the message and the second encapsulated portion of the message.

PRIORITY CLAIM

This application is a Continuation of U.S. Utility application Ser. No.14/673,553, filed Mar. 30, 2015, which is a Continuation of U.S. Utilityapplication Ser. No. 14/193,820, filed on Feb. 28, 2014, issued to U.S.Pat. No. 8,996,678 on Mar. 31, 2015, which is a Continuation of U.S.Utility application Ser. No. 13/471,109, filed on May 14, 2012, andissued to U.S. Pat. No. 8,667,115 on Mar. 4, 2014, which is aContinuation of U.S. Utility application Ser. No. 12/624,250, filed onNov. 23, 2009, and issued as U.S. Pat. No. 8,180,879 on May 15, 2012,which is a Continuation of U.S. Utility application Ser. No. 10/512,943,filed on Oct. 29, 2004, issued as U.S. Pat. No. 7,624,165 on Nov. 24,2009, which is a U.S. National Stage application of International PatentApplication Serial No. PCT/US2003/013443, filed Apr. 29, 2003, whichclaims the benefit of U.S. Provisional Application Ser. No. 60/377,631,filed on May 3, 2002, the contents of which are incorporated herein byreference in their entireties.

FIELD OF THE INVENTION

The following disclosure relates generally to communications systems,and more particularly, to maintaining persistent connections whileswitching within the same or to different networks operating indifferent frequency bands or utilizing different modes.

BACKGROUND OF THE INVENTION

Today there exist thousands of data and voice networks that utilize manydifferent communications protocols and technologies. The most basiclevel of a network is the infrastructure, the physical equipment thatutilizes power to send and receive electromagnetic, acoustic, or opticalsignals. The base communications protocol is a specific language thatenables the sending and receiving devices to talk to each other, makingsense of the signals. Additional protocols can be stacked on top of thebase protocol to create other languages that can be transported by thephysical devices. This higher-level language allows for communicationsover different types of infrastructures and signals.

A continuing trend is to enable communication between independentnetworks. This allows devices that could previously only communicate todevices on their respective network to communicate with devices on othernetworks. An example is the public Internet, a super network comprisedof a collection of networks utilizing many different infrastructuretechnologies transmitting many types of signals utilizing many types ofbase communications protocols. The uniting element is the IP transportlayer protocol, a common language known by each device.

Most devices are fixed and have one connection to a host network that inturn has a communications gateway for communications to other networks,such as the Internet. An example of this is the personal computer (PC)or telephone. There is typically no need for these devices to havemultiple host network connections.

However, other types of devices are portable, such as mobile phones,personal digital assistants (PDA), and laptop computers. These portabledevices typically need to have support for multiple network connections.A laptop computer often incorporates a modem to connect to a hostnetwork through a phone line when the laptop is at home and an Ethernetport to connect to the host network when the laptop is at the office.The laptop may also have an 802.11 (also known as “WiFi”) PCMCIA cardthat connects to the host network of a coffee shop or otherestablishment. Rarely is the laptop connected to a network or evenpowered up while in transit between destinations.

The mobile phone is connected to its host network nearly at all timesthe phone is activated. This connection is a much more complicatedprocess. The connection is established from the cell base station to thehandset via over-the-air electromagnetic signals using a variety ofcommunications protocols, such as TDMA, CDMA, GSM/GPRS, and the like.When the handset loses signal strength from one cell base station, itpicks up a signal from one or more geographically closer cell basestations that have a stronger signal. The handset establishes a hostnetwork connection with one of the closer cell base stations and thenterminates the original cell base station connection keeping the handsetpersistently connected to the network. This is called a connection“handoff” and is done today on mobile networks.

In the prior art, the handoff process can only be done within acarrier's physical network. For example, a Samsung phone communicatingwith the Sprint PCS network through a CDMA cell base station on the 2.3GHz frequency will not be able to transcend to another disparatenetwork, such as a GSM network operated by VoiceStrearn.

As voice and data networks come together there becomes a greater needfor persistent connections for mobile devices across multiple frequencybands, communications protocols, and host networks. This is due to theincreased processing power of a handheld device and the advancedservices that can now be offered to a mobile user.

Both wireless consumers and wireless carriers would benefit from theability to maintain persistent connections no matter where the consumermay be. As some of the advantages, connection quality can be improved,coverage can be expanded, costs can be lowered, premium data servicesmay be provided, reduced capital expenditures, and improved speed tomarket.

Thus, by seamlessly merging network resources through the use ofpersistent connection technology the following benefits are created:

Improvements for the Consumer:

-   -   1) Extended service range    -   2) Improved connection quality (most notably at work, home, and        events)    -   3) Lower cost with savings passed through from carrier due to        public network access savings    -   4) Secure communications for both voice and data    -   5) No roaming hassles for voice or data    -   6) Single device that works on multiple networks    -   7) Single user interface for both device and services    -   8) True benefits of broadband wireless sooner    -   9) New and improved data services

Benefits for the Carrier

-   -   1) Creates value added network through service offer        differentiation    -   2) Reduces capital investment required to build out broadband        network    -   3) Increases network usage by improving quality, expanding        coverage and supporting data services with all types of        infrastructures    -   4) Increases revenues through increased network usage and the        ability to offer premium services    -   5) Ultimately produces IT savings by standardizing on IP        communications protocol.    -   6) Reduces complexity of voice roaming    -   7) Naturally allows for data roaming    -   8) Utilizes excess wireline capacity

SUMMARY OF THE INVENTION

Embodiments provide an apparatus, system and method for communicating amessage between a mobile device and a destination device. An exemplaryembodiment has a first border server operable to establish a firstcommunication connection to the mobile device over a first networkoperating under a first protocol, wherein the first protocol isconfigured to communicate a first encapsulated portion of the message; asecond border server operable to establish a second communicationconnection to the mobile device over a second network operating under asecond protocol, wherein the second protocol is configured tocommunicate a second encapsulated portion of the message; and atransport management server communicatively coupled to the first borderserver and the second border server, and operable to establish a thirdcommunication connection to the destination device over a third networkoperating under a third protocol, wherein the third protocol isconfigured to communicate the first encapsulated portion of the messageand the second encapsulated portion of the message. The second networkis different from the first network. The second protocol is differentfrom the first protocol. And, the first communication connection and thesecond communication connection are concurrently established. These andother examples of the invention will be described in further detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a protocol layering diagram of the protocol stack used in themobile device.

FIG. 2 is a protocol layering diagram of the protocol stack used in thevarious servers at a network operations center (NOC).

FIG. 3 is a diagram representing a method of dividing up the varioussoftware components in the mobile device information modules.

FIG. 4 shows the physical network layout that could be used in the NOC.

FIG. 5 is a protocol diagram showing the steps involved in connectionestablishment.

FIG. 6 is a protocol diagram showing the steps involved in connectionteardown.

FIG. 7 is a protocol diagram showing the movement of data whileredundant multiplexing is in operation.

FIG. 8 is a protocol diagram showing the movement of data while switchedmultiplexing is in operation.

FIG. 9 is a protocol diagram which shows a connection handoff from onephysical connection to another caused by fading signal strength.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A method and apparatus for maintaining a persistent connection to atleast one network, such that said persistent connection can transcendvarious network protocols and infrastructures, is described in detailherein. In the following description, numerous specific details areprovided, such as specific wireless and wireline protocols, specifictypes of devices (laptops, cell phones, PDA's), to provide a thoroughunderstanding of, and enabling description for, embodiments of theinvention. One skilled in the relevant art, however, will recognize thatthe invention can be practiced without one or more of the specificdetails, or with protocols or devices, methods, etc. In other instances,well-known structures or operations are not shown, or are not describedin detail, to avoid obscuring aspects of the invention.

The description below describes a method and system to merge separatephysical networks consisting of multiple frequency bands, communicationsprotocols, and hosts by creating a logical network layer that is capableof keeping a persistent connection with a stationary or in motiondevice.

The description below describes a method and system to provide multipleconnections to a device from separate physical networks through the samelogical network layer that keeps connections persistent. In order tokeep connections persistent and change physical networks at least oneadditional connection is needed to seamlessly accomplish the “hand-off”.Multiple connections can increase the overall signal strength to thedevice. If one or more signals from the network host to the device areweek or degraded then multiple connections can provide redundancy ofdata being sent from the host to the device reducing the amount of lostdata. Multiple connections can be used to increase the amount of datathat can be sent to the device at any given time, the bandwidth. This isdesirable because it improves the efficiency of frequency usage byallocating it in an on demand manner. Also, data delivery rates canincrease, which improves the services the device can support.Furthermore, it is desirable to increase the rate data is transmitted tothe device without replacing existing physical infrastructure orlicensing new spectrum.

The description below describes a method and system that provides thislogical network layer in a way that requires no modifications in theunderlying hardware or software required by the physical network host orthe device. This approach is taken to provide backward and forwardcompatibility for physical infrastructure, communications protocols andsignal type. It does not preclude the embedding of the present inventioninto future versions of software or hardware in the areas stated above.On the contrary, it is expected that the inclusion of the presentinvention will decrease the size and complexity of future productversions. This network neutral approach is possible through the additionof the client software on the device and the use of the presentinvention's server software at the NOC. Thus, no special alteration ofthe physical network is needed to deploy the present invention.

The description below describes a method and system that makes use ofboth voice and data physical networks to keep multiple persistentconnections in such a way that the logical network layer can deliverboth voice and data communications through any connection regardless ofthe primary intent of the physical network. This is accomplished throughthe present invention by providing a digital-based or packet-basedLogical network layer on top of the physical network. This allows fornon-digital communications protocols to carry digital protocols. Inaddition voice communication is digitally represented at the logicalnetwork layer regardless of how the voice communication was initiated.This is commonly referred to as VOIP.

The description below describes a method and system that merges separatephysical networks through persistent multiple connections in a way thatdoes not interfere with or require a change in the way the physicalnetwork identifies the device for either data or voice connectionestablishments or communication transmissions. The present inventionaccommodates this through the use of device ID, phone number and deviceassigned IP “transparency”. “Transparency” in this case means that thephysical networks identify the device in the same manner they docurrently. This is typically done through the assignment of a phonenumber or IP to the ID of the device or to the SIM card accompanying thedevice. Usually this is done during the process of activation orregistration but could also be done at the time the device connects tothe host physical network, authentication. The present invention passesthis identification information to the appropriate physical network foreach connection. However, “transparency” also means that the logicalnetwork layer masks this information from any portion of the deviceabove the logical layer protocol stack. Similarly, the NOC outside ofthe present invention's multiplex and connection servers only identifiesthe device by the ID assigned by the logical network layer. Additionallythe physical network is only aware of the connection that it has withthe device. Thus, connections from other physical networks to the deviceare transparent from each other. When connection requests are made tothe device from other devices the logical ID is used, which wouldtypically be a published phone number or IP.

The description below describes a method and system for providing apersistent connection utilizing multiple physical network connections toa single device. The system is created through client and serversoftware that creates a logical network layer that controls thecommunications to the device. This includes controlling both voice anddata connections and transmissions and controlling the establishment and“hand-offs” of physical connections. The system provides for themonitoring of aggregate signal strength to the device and controllingthe data transmission by optimizing for week signal redundancy ormultiplexing connections to increase bandwidth. Additionally the systemcreates connection “transparency” for both the physical networks andexternal devices. Maintaining a device does this through alogical\physical network ID table and routing provided by the servermultiplex and connection software.

Unless described otherwise below, the construction and operation of thevarious blocks shown in the Figures are of conventional design. As aresult, such blocks need not be described in further detail herein,because they will be understood by those skilled in the relevant art.Such further detail is omitted for brevity and so as not to obscure thedetailed description of the invention. Any modifications necessary tothe blocks in the Figures (or other embodiments) can be readily made byone skilled in the relevant art based on the detailed descriptionprovided herein.

Further, where protocol layers and stacks are shown in the Figures, thistype of description is known in the art, and can itself include variousdetails that need not be described herein. Those skilled in the relevantart can create source code, microcode, program logic arrays or otherwiseimplement the invention based on the Figures and the detaileddescription provided herein. Further, while many of the embodiments areshown and described as being implemented in software, such embodimentscould equally be implemented in hardware and be performed by one or moreprocessors.

Further, the Figures and the associated discussion provide a generaldescription of a suitable environment in which aspects of the inventioncan be implemented. Although not required, embodiments of the inventionwill be described in the general context of computer-executableinstructions running on various devices. Those skilled in the relevantart will appreciate that aspects of the invention can be practiced withother computer system configurations, including Internet appliances,hand-held devices, wearable computers, cellular or mobile phones,multi-processor systems, microprocessor-based or programmable consumerelectronics, set-top boxes, network PCs, mini-computers, mainframecomputers and the like. Aspects of the invention can be embodied in aspecial purpose computer or data processor that is specificallyprogrammed, configured or constructed to perform one or more of thecomputer-executable instructions explained in detail below.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “above,” “below” and words of similar import, when usedin this application, shall refer to this application as a whole and notto any particular portions of this application. When the claims use theword “or” in reference to a list of two or more items, that word coversall of the following interpretations of the word: any of the items inthe list, all of the items in the list and any combination of the itemsin the list.

Overview of Protocols

To facilitate user logical transparency, and physical networkindependence, the Transport Layer of the present invention (referred toas “CoCo”) uses a number of protocols, some standard and some developedspecifically for the purpose of the invention. In FIGS. 1 and 2 theseprotocols and their interrelations are shown. FIG. 4 shows thearchitecture of a network and mobile device 35 implementing the presentinvention. The logical transparency exists between layers 3 and 17, inthat IP traffic originating on either the network side or the mobiledevice side is transported to and from the underlying network to theother unmodified. In fact, the multiplex server acts as a proxy onbehalf of the mobile device.

The IP traffic is encoded and tagged with addressing information duringit's passage to the CoCo Multiplex layer 4 an 18. This information isused by the intermediary machines such as the border server 45-47.Information between the border servers 45-47 and the mobile device 35 isfurther encoded using an encapsulation mechanism 7 and 15 specific tothe underlying protocol (in this example CDMA), and then transportedusing that underlying protocol 8 and 16. Once arriving on the borderserver 45-47, parts of the Multiplex Subset 48 communicate using CoCoMultiplex over UDP (13, 19, 23).

The CoCo Multiplex Protocol is also used to allow the transportmanagement module (28) and the transport management server (52) tocommunicate via layering another protocol, the transport managementprotocol (9,21) on top of CoCo Multiplex Protocol (4, 22).

Overview of Software Components in Mobile Device

FIG. 3 details a method of componentizing the software within the mobiledevice 35. The interface 25 is the means by which other portions of thesoftware on the mobile device 35 communicate over the CoCo TransportLayer. The TCP/IP stack 26 is a normal TCP/IP stack similar to networksoftware component of any network operating system. The TMM (TransportManagement Modules, 28) though the interfacing 25 is instructed tomodify the connection (for example, bringing the entire virtualconnection (not a component physical connect) up and down, or changingthe tuning parameters used to decide what physical networks to use). TheTMM 28 also receives information about the connection state from thevarious connection modules, of which three examples were given 29, 30,31. The TMM 28 also communicates with the MINI (Multiplex Module, 27),to change it's settings.

The MM 27 is in charge of actual data transport for the TCP/IP Stack 26to the Connection Modules 29, 30, 31. The manner of subdividing thetransport among the modules will be discussed in more detail below. Thevarious connection modules 29, 30, 31 are in charge of doingencoding/decoding for their respective encapsulation layers 5, 7, 10 andpassing the results to their respective drivers 32, 33, 34 whichcommunicate to the lower level protocol layers 6, 8, 100, and eventuallyhardware.

Overview of the NOC (Network Operations Center) Transport Subsystem—

The NOC is the point of aggregation of all the various data paths usedby the mobile device 35, and the external address location of themobile. As is shown in FIG. 4, the mobile device 35 communicates viamultiple technologies along various paths (such as 35->36->39->42->45 or35->37->40->43->46), all of which terminate at a border server 45-47.This entire communication takes place using network addressing andprotocols known to the hardware doing the transport (for example CDMAfor CDMA networks), and does not require any of the intermediarycomponents (along the paths above) to understand any of the CoCoprotocols or make any special provisions.

Once arriving at a border server 45, 46, 47, the data is deencapsulatedvia the border server using it's understanding of the underlyingtechnology (for example, 15, and 16 for CDMA). That is, each borderserver understands only how to deal with a specific technology inrelation to encapsulation and transport. Once the deencapsulation isdone, the border server should have a CoCo Multiplex 12 protocolmessage, which is either an encapsulated IP datagram 3 or a transportmanagement protocol datagram 9. This is delivered to the appropriateplace via encoding the CoCo Multiplex Protocol message in UDP 13 andsending it to the correct destination over the Multiplex Subnet 48.

There are various multiplex servers 49-52 each of which is assigned toone or more mobile devices, and acts as the device's proxy in relationto data transfer. There is also a transport management server 52 whichmanages connection state information for all mobile devices. This TMS 52can be addressed via any machine on the Internal Subnet 53. Also, anymachine on the Internal Subnet 53 can communicate to a given mobiledevice as though it were local by simply address it's proxy multiplexserver (50 perhaps). If it is desired to make the mobile device 35addressable from an external network (the Internet for example), routingcan be set up to allow the multiplex server 50, to be made available tothe external network through a gateway (part of 54) which is on theinternal network 53.

One should note that the border servers 45-47 are all multi-homed onboth the multiplex subnet 48 and a network specific to their ownencapsulation method (42, 43, and 44 respectively). The multiplexservers (45, 46, 47) and the TMS 52 are similarly multi-homed, butbetween the Multiplex Subset 48 and an internal subnet 53. Note: it isnot a requirement that there be a single internal subnet, differentmultiplex servers could be on different internal subnets, also, the TMS52 does not have to be on the same internal subnet as the multiplexservers. In fact, if the internal subnet containing the multiplexservers is made externally addressable it would be advantageous from asecurity perspective for the TMS to go to its own subnet.

Connection Establishment/Teardown

The term “connection” refers to a given data path between the mobiledevice and the NOC, that is a specific set of hardware, protocols andaddressing which can be used to move data from the mobile to the NOC.Further, the connection can refer to the communication of voice or dataor both over the network. The virtual connection idea seen by the higherlayers is a purely software construct whose state depends on theunderlying connections. In this section when the term “connections” isused, this refers to the underlying, physical connections, not thetransparent virtual one.

The decision to bring a given connection up or down is made by thetransport management module 28, and the transport management server 52.Usually, the decisions will be made via the mobile device 35, butsupport exists for any form of negotiation or control between the twotransport managers. The overall goal of the transport managementprotocol (21, 9) is to convey information between the two transportmanagers, so that they are both aware of the same current connectionstatus. However, there are times when they must independently modifytheir own state, such as an unexpected connection close.

The transport managers use information from the user (other modules 25for TMM 28, or other subsystems 54 for TMS), from the connection(connection modules 29-31 for the TMM 28, or border servers 45-47 forthe TMS 54), and from the other transport manager to make decisions onconnection changes.

The process of establishing a new connection over another physicaltransport mechanism is shown in FIG. 5. In this Figure, the mobiledevice 35 has decided to initiate the connection. Should the NOC havedecided to initiate the connection, the diagram would look similar, withthe TMM 55 switched with the TMS 60, the MINI 56 switched with the MS59, and the CM 57 switched with the base station 58.

The communications in the diagram represent asynchronous function callsbetween the modules, CoCo Multiplex over UDP between the various NOCServers, and a particular encapsulation methods between the connectionmodule 57 and the border server 58.

Walking Through of FIG. 5:

-   -   61. The TMM 55 decides to initiate a new connection using method        X.    -   62. It alerts the correct connection module    -   63. Which opens the physical connection.    -   64. Which the connection modules notes,    -   65. And alerts the TMM    -   67. Which changes it's state and modifies the NM's settings as        desired

Meanwhile, on the other side of the connections

-   -   63. The Border Server receives the connections, causing it to    -   66. Alert the TMS of the new connections    -   68. Which then changes it's state and modifies the MM's settings        as desired.

FIG. 6 shows the similar process of connection teardown. Again, theprocess is shown based on the mobile device causing the teardown. Bymaking the same replacements described in the establishment section, thediagram would show the NOC causing the teardown. In the case of aspontaneous connection break, the connection module 71 and the borderserver 72 both alert the TMM 69 or the TMS 74 respectively via an ‘AlertClosed’ signal 79, which causes both sides to perform a ‘Remove Con’action 80, resulting in a disconnected state.

Walking Though the Normal Case:

-   -   75. A close is initiated    -   76. The TMM removes the connection from the MM's 70 list,        resulting in no further data being sent over the connection, as        well as    -   77. Telling the correct CM 71 to close the module    -   78. Which it does    -   79. Resulting in the BS 72 noticing the close and alerting the        TMS 74    -   80. Which calls ‘Remove Con’ 80 on the MS 73, resulting in no        more data being sent over the connection in the reverse        direction

Overview of Multiplexing (Redundancy and Switching)

Mutliplexing refers to using more than one physical/logical network totransport data for a single higher level logical connection (the virtualconnection). Two types of multiplexing are supported: Redundant andSwitched. Redundant multiplexing involve sending the same data over morethan one path, thus improving the chances for correct reception.Switched multiplexing involve splitting the data over multipleconnections to improve throughput.

The CoCo model support both, including both simultaneously. For example,assume there are three physical connections, A, B, and C. One couldalways send data over C, as well as either A or B, switching betweenthem. One could also use switched or redundant multiplexing across threeor more parts. The two simplest cases (two connection switchedmultiplexing and two connection redundant multiplexing) are examined inFIGS. 7 and 8, as detailed below

Data Transport in Two Connection Redundant Multiplexing

In FIG. 7, we see data moving from the mobile to the NOC. The reverseprocess (moving data from NOC to mobile) is identical with the changesdiscussed in the connection section.

We begin with a packet entering at 89. The multiplex module 82 thensends the packet to both of the Connection Modules 83 and 84 as seen in(90, 92). Once at each module, the data is encapsulated and sent 91 and94 to the respective border server at 85 and 86. Once the data isdeencapsulated and sent (93, 95) to the multiplex server 87. Uponreceiving the first packet 93 the multiplex server send the data overthe internal network 96 to it's final destination. The second packet 95is dropped. If however the first packet had been unable to make it, thesecond packet would have resulted in data still making it across.

Data Transport in Two Connection Switched Multiplexing

In FIG. 7, we see data moving from the mobile to the NOC. The reverseprocess (moving data from NOC to mobile) is identical with the changesdiscussed in the connection section.

We begin with packets 1 (105) arriving from the IP stack. Once in theMINI 98 one of the two connections modules is chosen based on currenttraffic conditions/cost/bandwidth/etc. In this case, CM A 99. The datais then sent at 106 to CM A (99) where it is encapsulated and send (107)to BS A (101) where it is deencapsulated and sent 108 to MS 103 whichthen forwards the data portion over the internal network to it's finaldestination 104.

Packet 2 arrives (110) and another CM is chosen, B in this case (100),the packet travels (111, 112, 113) to the same MS (103) at the NOC, andis sent in the same manner as the proceeding packet 1 to (104).

Use of Connection Redundancy During Handoff

FIG. 9 puts all the parts together and gives an example of a transparentconnection handoff. We start out with normal data transfer over a singleconnection (123). The process really gets started when the connectionmodule being used to deliver the data (Connection Module A, 117) noticesa weakening signal strength and alerts (124) the TMM(115). At this pointthe TMM(115) begins a connection establishment over path B (125), usingthe methods diagramed in FIG. 5. Once this connection is established,the data flows using redundant multiplexing (126) as detailed in FIG. 7.Upon fully losing signal (127), the connection over A is torn down,which being a connection caused teardown is a modification of FIG. 6 asdiscussed in the section on connection teardown. This changes the MM(116) to now use the single connection B for it's data transfer, thuscompleting the handoff.

The above detailed descriptions of embodiments of the invention are notintended to be exhaustive or to limit the invention to the precise formdisclosed above. While specific embodiments of, and examples for, theinvention are described above for illustrative purposes, variousequivalent modifications are possible within the scope of the invention,as those skilled in the relevant art will recognize. For example, whilesteps are presented in a given order, alternative embodiments mayperform routines having steps in a different order. The teachings of theinvention provided herein can be applied to other systems. These andother changes can be made to the invention in light of the detaileddescription.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. Aspects of the invention can bemodified, if necessary, to employ the systems, functions and concepts ofthe various patents and applications described above to provide yetfurther embodiments of the invention.

These and other changes can be made to the invention in light of theabove detailed description. In general, the terms used in the followingclaims, should not be construed to limit the invention to the specificembodiments disclosed in the specification, unless the above detaileddescription explicitly defines such terms. Accordingly, the actual scopeof the invention encompasses the disclosed embodiments and allequivalent ways of practicing or implementing the invention under theclaims.

1. A method of communicating a message between a mobile device and adestination device via a network operations center, wherein the networkoperations center is communicatively coupled to a first border serverthat is concurrently communicatively coupled to the mobile device over afirst connection of a first communication system operating under a firstprotocol, wherein the network operations center is communicativelycoupled to a second border server, and wherein the network operationscenter is communicatively coupled to the destination device, the methodcomprising: encapsulating, at the mobile device, a first portion of themessage into an encapsulated first packet using the first protocol;communicating the encapsulated first packet of the message from themobile device to the first border server over the first connection; inresponse to a weakening of the signal strength of communications overthe first connection, communicatively coupling the mobile device to thesecond border server over a second connection of a second communicationsystem operating under a second protocol, wherein the secondcommunication system is different from the first communication system,encapsulating, at the mobile device, a second portion of the messageinto an encapsulated second packet using the first protocol and into anencapsulated third packet using the second protocol; and substantiallyconcurrently communicating the encapsulated second packet of the messagefrom the mobile device to the first border server over the firstconnection and communicating the encapsulated third packet of themessage from the mobile device to the second border server over thesecond connection.
 2. The method of claim 1, further comprising:monitoring signal strength of communications over the first connection.3. The method of claim 1, further comprising: in response to a completeloss of signal over the first connection, closing the first connectionbetween the mobile device and the first border server.
 4. The method ofclaim 3, wherein the first connection fails when a capacity of the firstconnection decreases below the threshold.
 5. The method of claim 3,further comprising: in response to closing the first connection,encapsulating, at the mobile device, a subsequent third portion of themessage into an encapsulated fourth packet using the second protocol;and communicating the encapsulated fourth packet of the message from themobile device to the second border server over the second connection. 6.The method of claim 1, wherein the mobile device is a laptop computer.7. The method of claim 1, wherein the first protocol of the firstconnection is a wireline protocol, and wherein communicatively couplingthe mobile device to the second border server over the second connectionof the second communication system operating under the second protocolcomprises: communicatively coupling the mobile device to the secondborder server over the second connection of the second communicationsystem operating according to a WiFi protocol.
 8. The method of claim 1,wherein the first protocol of the first connection is a Wi-Fi protocol,and wherein communicatively coupling the mobile device to the secondborder server over the second connection of the second communicationsystem operating under the second protocol comprises: communicativelycoupling the mobile device to the second border server over the secondconnection of the second communication system operating according to aCDMA protocol.
 9. The method of claim 1, wherein the first protocol ofthe first connection is a Wi-Fi protocol, and wherein communicativelycoupling the mobile device to the second border server over the secondconnection of the second communication system operating under the secondprotocol comprises: communicatively coupling the mobile device to thesecond border server over the second connection of the secondcommunication system operating according to a GSM protocol.
 10. Themethod of claim 1, further comprising: redundantly multiplexingcommunication via the first and second connection; upon fully losing thesignal of the first connection, communicating only via the secondconnection.
 11. A mobile device that communicates messages with adestination device via a network operations center, wherein the networkoperations center is communicatively coupled to a first border serverthat is concurrently communicatively coupled to the mobile device over afirst connection of a first communication system operating under a firstprotocol, wherein the network operations center is communicativelycoupled to a second border server, and wherein the network operationscenter is communicatively coupled to the destination device, the mobiledevice comprising: a processor; and logic that is configured, whenexecuted by the processor, to: encapsulate a first portion of themessage into an encapsulated first packet using the first protocol;communicate the encapsulated first packet of the message from the mobiledevice to the first border server over the first connection; in responseto a weakening of the signal strength of communications over the firstconnection, communicatively couple the mobile device to the secondborder server over a second connection of a second communication systemoperating under a second protocol, wherein the second communicationsystem is different from the first communication system, encapsulate, atthe mobile device, a second portion of the message into an encapsulatedsecond packet using the first protocol and into an encapsulated thirdpacket using the second protocol; and substantially concurrentlycommunicate the encapsulated second packet of the message from themobile device to the first border server over the first connection andcommunicating the encapsulated third packet of the message from themobile device to the second border server over the second connection.12. The mobile device of claim 11, wherein the logic is furtherconfigured to: monitor signal strength of communications over the firstconnection.
 13. The mobile device of claim 11, wherein the logic isfurther configured to: in response to a complete loss of signal over thefirst connection, close the first connection between the mobile deviceand the first border server.
 14. The mobile device of claim 13, whereinthe first connection fails when a capacity of the first connectiondecreases below the threshold.
 15. The mobile device of claim 13,wherein the logic is further configured to: in response to closing thefirst connection, encapsulate, at the mobile device, a subsequent thirdportion of the message into an encapsulated fourth packet using thesecond protocol; and communicate the encapsulated fourth packet of themessage from the mobile device to the second border server over thesecond connection.
 16. The mobile device of claim 11, wherein the mobiledevice is a cellular phone.
 17. The mobile device of claim 11, whereinthe first protocol of the first connection is a wireline protocol, andwherein the logic is further configured to: communicatively couple themobile device to the second border server over the second connection ofthe second communication system operating according to a WiFi protocol.18. The mobile device of claim 11, wherein the first protocol of thefirst connection is a Wi-Fi protocol, and wherein the logic is furtherconfigured to: communicatively couple the mobile device to the secondborder server over the second connection of the second communicationsystem operating according to a CDMA protocol.
 19. The mobile device ofclaim 11, wherein the first protocol of the first connection is a Wi-Fiprotocol, and wherein the logic is further configured to:communicatively couple the mobile device to the second border serverover the second connection of the second communication system operatingaccording to a GSM protocol.
 20. The mobile device of claim 11, whereinthe logic is further configured to: redundantly multiplex communicationvia the first and second connection; upon fully losing the signal of thefirst connection, communicate only via the second connection.